From a99c711b249fda41aa1e5f551f1508b7c36c3831 Mon Sep 17 00:00:00 2001 From: "kaf24@firebug.cl.cam.ac.uk" Date: Wed, 24 Aug 2005 10:48:24 +0000 Subject: [PATCH] Initialise syscall32 vsyscall page early, as it may be needed for some initcalls (e.g., if initrd /bin/hotplug is an i386 binary). Signed-off-by: Keir Fraser --- linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c b/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c index ecccf66a2e..24cb4c4cc6 100644 --- a/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c +++ b/linux-2.6-xen-sparse/arch/xen/x86_64/ia32/syscall32.c @@ -128,8 +128,12 @@ static int __init init_syscall32(void) #endif return 0; } - -__initcall(init_syscall32); + +/* + * This must be done early in case we have an initrd containing 32-bit + * binaries (e.g., hotplug). This could be pushed upstream to arch/x86_64. + */ +core_initcall(init_syscall32); /* May not be __init: called during resume */ void syscall32_cpu_init(void) -- 2.30.2